System and method to facilitate interoperability of health care modules

ABSTRACT

A system for facilitating interoperability among health care modules includes an interface configured to receive a first electronic record from a first health care module. The first electronic record has a first data structure. The system also includes a processor communicatively coupled to the interface. The processor is configured to analyze the first electronic record having the first data structure, and, based on the analysis, extract a portion of data from the first electronic record. The processor further creates a second electronic record using the portion of data from the first electronic record, where the second electronic record has a second data structure. The second data structure is configured to be compatible with a second health care module. The interface is further configured to transmit the second electronic record for display to the second health care module.

PRIORITY

This application is a continuation, under 35 U.S.C. § 120, of U.S.patent application Ser. No. 17/084,973 filed on Oct. 30, 2020 which is acontinuation, under 35 U.S.C. § 120 of U.S. patent application Ser. No.15/715,359 filed on Sep. 26, 2017 and entitled “System And Method ToFacilitate Interoperability Of Health Care Modules” incorporated hereinby reference.

TECHNICAL FIELD

The present disclosure relates generally to health care modules and,more specifically, to a system and method to facilitate interoperabilityof health care modules.

BACKGROUND

Health care organizations typically comprise their own computer systems,modules, and electronic records for storing information about patients,health care professionals, pharmacies, and insurance companies. Therecords may be incompatible such that the information within the recordscannot be easily shared or understood by separate health careorganizations and modules. Current practices for communicating andsharing electronic records in the health care industry are limited.

SUMMARY OF EXAMPLE EMBODIMENTS

According to embodiments of the present disclosure, disadvantagesassociated with incompatibility among various health care modules may bereduced or eliminated.

In accordance with a particular embodiment of the present disclosure, asystem for facilitating interoperability among health care modulesincludes an interface configured to receive a first electronic recordfrom a first health care module. The first electronic record has a firstdata structure. The system also includes a processor communicativelycoupled to the interface. The processor is configured to analyze thefirst electronic record having the first data structure, and, based onthe analysis, extract a portion of data from the first electronicrecord. The processor further creates a second electronic record usingthe portion of data from the first electronic record, where the secondelectronic record has a second data structure. The second data structureis configured to be compatible with a second health care module. Theinterface is further configured to transmit the second electronic recordfor display to the second health care module.

In accordance with another aspect of the present disclosure, a methodfor facilitating interoperability among health care modules includesreceiving, by an interface, a first electronic record from a firsthealth care module, where the first electronic record having a firstdata structure. The method also includes analyzing, by a processor, thefirst electronic record having the first data structure, and based onthe analysis, extracting, by the processor, a portion of data from thefirst electronic record. The method further includes, creating, by theprocessor, a second electronic record using the portion of data from thefirst electronic record, the second electronic record having a seconddata structure, wherein the second data structure is configured to becompatible with a second health care module. The method finally includestransmitting, by the interface, the second electronic record for displayto the second health care module.

In accordance with another aspect of the present disclosure, anon-transitory computer-readable medium encoded with logic, the logic,when executed by a processor, is operable to receive a first electronicrecord from a first health care module, where the first electronicrecord having a first data structure. The logic is further operable toanalyze the first electronic record having the first data structure, andbased on the analysis, extract a portion of data from the firstelectronic record. The logic is further operable to create a secondelectronic record using the portion of data from the first electronicrecord, where the second electronic record having a second datastructure. The second data structure is configured to be compatible witha second health care module. Finally, the logic is operable to transmitthe second electronic record for display to the second health caremodule.

Technical advantages of particular embodiments of the present disclosureinclude reconfiguring an existing data structure to create a new datastructure to allow health care modules to communicate health careinformation between disparate components. This improvement alleviatescompatibility concerns between different systems components, therebycreating increased flexibility in exchanging electronic records.Additionally, a system may be configured to analyze data in anelectronic record and extract a portion of data from the electronicrecord, thereby conserving the computational resources and bandwidthconsumed by unnecessarily extracting all of the data, some of which maybe irrelevant.

In an embodiment, a system is configured to create a first user profileand associate the first user profile with other user profiles, therebyconserving the computational resources and bandwidth consumed by addingadditional information contained in other user profiles to the firstuser profile.

In an embodiment, a system is configured to create a second electronicrecord that is compatible with more than one health care module, therebyconserving the computational resources and bandwidth consumed bycreating and maintaining duplicate electronic records, each in adifferent format unique to each health care module.

Other technical advantages of the present disclosure will be readilyapparent to one skilled in the art from the following figures,descriptions, and claims. Moreover, while specific advantages have beenenumerated above, various embodiments may include all, some, or none ofthe enumerated advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and forfurther features and advantages thereof, reference is now made to thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates an example system that facilitates interoperabilityof health care modules;

FIG. 2 illustrates an example flowchart for a method for various usersof a system to register and create user profiles to facilitateinteroperability among health care modules;

FIG. 3 illustrates an example flowchart for facilitatinginteroperability between a health care professional module and aninsurance module;

FIG. 4 illustrates an example flowchart for facilitatinginteroperability between a pharmacy module and health care professionalmodule;

FIGS. 5A-C illustrate example user profiles that may facilitateinteroperability among health care modules; and

FIG. 6 illustrates an example interface for creating a new prescriptionand facilitating interoperability between health care professionalmodules, patient modules, and pharmacy modules.

DETAILED DESCRIPTION

Embodiments of the present disclosure and its advantages are bestunderstood by referring to FIGS. 1-6 , like numerals being used for likeand corresponding parts of the various drawings.

Current practices in the health care industry include various ways ofstoring, maintaining, accessing, and analyzing electronic documents,such as medical records, insurance information, prescriptioninformation, and any other information or document used by those in thehealth care industry. For example, health care professionals,pharmacies, insurance companies, and others may each have separatemodules, systems, data, and records, that are maintained in differentways such that electronic information cannot be easily shared amongthem. By having such disparate record-keeping and information-storingpractices, it makes coordination among the modules in the health careindustry difficult, time consuming, and inefficient. For example, if apatient goes to see four different health care professionals, eachhealth care professional may maintain its own electronic health recordsusing a specific program and/or specific format. These electronic healthrecords cannot be shared among the four health care professionalsbecause one format of a health record at one health care professional'soffice would not be recognized or understood by another system such thatthe data may be incorporated into each unique system. Further, theinformation cannot be easily shared such that each health careprofessional receives up-to-date patient information, and can coordinateon the patient's health. Instead, a patient must fill out new, updatedhealth forms during each visit to the health care professional's office,which must then be entered into its own electronic health record system,thus expending additional computational resources as well as employeetime.

As another example, a pharmacy or fulfillment center may have acompletely different system and electronic health records than aninsurance company or payee. When a pharmacy employee needs to fulfill aprescription by a health care professional for a patient, it cannot sendany electronic information to the insurance company due to the differentsystems and modules at each. If a pharmacy employee attempted totransmit electronic prescription information to the insurance company,the insurance company's system would not be able to accurately accessthe information needed to determine whether a prescription is covered.Instead, a pharmacy employee must manually contact the insurance company(e.g., by phone) and have an employee of the insurance company enter therelevant information, determine whether a prescription is covered, andthen provide the coverage information to the pharmacy employee. It is aninefficient system that requires duplication in electronic medical,health, and pharmaceutical records. Certain databases commonly used inthe health care industry to provide information about health careprofessionals, medical conditions, or drug information may similarlymaintain data in particular formats such that accessing information fromany of them may require a unique module and/or data processing system.

Thus, it may be desirable to have a system that facilitatesinteroperability among the various organizations, medical professionals,systems, and electronic data formats used in the health care industry.The teachings of this disclosure recognize that the use of differentsystems and formats for electronic records may prevent those in themedical industry from sharing electronic records regarding healthinformation. By facilitating interoperability among health care modules,electronic records in various formats and health information may beefficiently and accurately shared, thus conserving computationalresources and bandwidth consumed by unnecessarily maintaining duplicatecopies of the same data in different formats at each of the varioussystems.

FIG. 1 illustrates an example system 100 that facilitatesinteroperability of health care modules and databases. System 100 mayinclude interoperability module 140, patient module 110, health careprofessional module 120, pharmacy/fulfillment module 130,insurance/payee module 150, medical conditions database 182, NationalProvider Identifier (NPI) number database 183, Drug EnforcementAdministration (DEA) number database 184, National Council forPrescription Drug Programs (NCPDP) database 185, National Drug Code(NDC) database 181, and Durable Medical Equipment (DME) provider module170. System 100 may be connected by network 105.

In general, interoperability module 140 receives a first electronicrecord from a first health care module, the first electronic recordhaving a first data structure. Interoperability module 140 may furtheranalyze the first electronic record having the first data structure,and, based on the analysis, extract a portion of data from the firstelectronic record. Interoperability module 140 may also create a secondelectronic record using the portion of data from the first electronicrecord, the second electronic record having a second data structure. Thesecond data structure may be configured to be compatible with a secondhealth care module. Finally, interoperability module 140 may be furtherconfigured to transmit the second electronic record for display to thesecond health care module.

Network 105 may refer to any interconnecting system capable oftransmitting audio, video, signals, data, messages, or any combinationof the preceding. Network 105 may include all or a portion of a publicswitched telephone network (PSTN), a public or private data network, alocal area network (LAN), a metropolitan area network (MAN), a wide areanetwork (WAN), a local, regional, or global communication or computernetwork such as the Internet, a wireline or wireless network, anenterprise intranet, a cellular network, or any other suitablecommunication link, including combinations thereof.

Network 105 may communicatively couple the various modules (e.g.,patient module 110, health care professional module 120, fulfillmentmodules (i.e., pharmacy module 130 and DME provider module 170), and/orinsurance module 150) and databases (e.g., medical conditions database182, NPI number database 183, DEA number database 184, NCPDP database185, HCPCS database 186, and/or NDC database 181) of system 100 tointeroperability module 140.

In some embodiments, system 100 comprises a number of modules thatservice different entities and/or organizations in the health careindustry. These modules may include patient module 110, health careprofessional module 120, pharmacy module 130, insurance module 150, andDME provider module 170.

Modules 110, 120, 130, 150, and 170 may be any suitable combination ofhardware and/or software implemented in one or more modules to processdata. In some embodiments, each module may be accessed by users 135 a-dutilizing user devices 115 a-d. Each module may store electronicrecords, such as patient health records, insurance information (e.g.,prescription coverage and deductibles), medication and fulfillmentinformation, or any other records relating to health care. For example,health care professional module 120 may track patient information,health care records, and appointment schedules. As another example,insurance module 150 may track patient information, prescriptioninformation, and deductible information. In some embodiments, patientmodule 110 may need access to an electronic record from health careprofessional module 120 (e.g., prescription information).Interoperability module 140, in some embodiments, may facilitate patientmodule 110 accessing electronic records from health care professionalmodule 120. Interoperability module 140 may receive a request frompatient module 110 regarding electronic records, determine the necessaryrecords, and extract the necessary portion of data from the necessaryelectronic records. For example, patient module 110 may request certaininformation about a prescription, such as dosage instructions, andinteroperability module 140 may access all the prescription informationfrom health care professional module 120, extract the dosageinstructions, and provide that information to patient module.

User devices 115 a-d may refer to any device that allows users 135 a-dto communicate with and receive information from other modules in system100 through interoperability module 140. In some embodiments, userdevices 115 a-d may include a computer, workstation, telephone, Internetbrowser, electronic notebook, Personal Digital Assistant (PDA), pager,or any other suitable device (wireless, wireline, or otherwise),component, or element capable of receiving, processing, storing, and/orcommunicating information with other components of system 100. Userdevices 115 a-d may also comprise any suitable user interface such as adisplay, microphone, keyboard, electronic pen, or any other appropriateterminal equipment usable by user 135 a-d. It will be understood thatsystem 100 may comprise any number and combination of user devices 115a-d. Users 135 a-d utilize user devices 115 a-d to interact withinteroperability module 140 and other modules of system 100, asdescribed below. In some embodiments, users 135 a-d may be a patient,caregiver, heath care professional, pharmacists, technician, insuranceadministrator, or any other person needing to access a component ofsystem 100.

Patient module 110 may be any suitable combination of hardware and/orsoftware implemented in one or more modules to process data for user 135a, such as a patient or caregiver for a patient. Patient module 110 maystore and process data related to patient 135 a, such as medicalrecords, prescription information (i.e., for medications, drugs, medicalequipment and devices, and/or any other wellness benefit), medicalconditions, preferred pharmacies, or any other information related tothe health of patient 135. In some embodiments, user 135 may be acaregiver that provides care to a patient. Examples of caregivers 135 amay be a parent of a child patient, a family member, an in-home nurse ortechnician for a sick and/or elderly patient, a nursing home attendant,or anyone tasked with providing care to patient 135 a. In someembodiments, caregivers 135 a may be able to access patient module 110for one or more patients 135 a to which caregiver 135 a is providingcare. In some embodiments, system 100 does not include patient module110, and patient 135 a may store all of the health records of thepatient in interoperability module 140. Patient 135 a may utilize userdevice 115 a through network 105 to input and receive information frominteroperability module 140 and other components of system 100. In someembodiments, interoperability module 140 facilitates patient module 110operating in conjunction with other modules, such as health careprofessional module 120, pharmacy module 130, DME provider module 170,and/or insurance module 150.

Health care professional module 120 may be any suitable combination ofhardware and/or software implemented in one or more modules to processdata for user 135 b, such as a doctor, nurse practitioner, physician'sassistant, technician, administrative assistant, or any other employeeworking with a health care professional. Health care professional module120 may store and process data related to health care professional 135 b(e.g., NPI number, DEA number, taxonomy, specialties, address, and/orphone number), health care information, and records of one or morepatients 135 a, or any other information related to health careprofessional 135 b. In some embodiments, health care professional module120 is associated with a physical location, such as a hospital ordoctor's office. In some embodiments, system 100 does not include healthcare professional module 120, and health care professional 135 b maystore all of the records in interoperability module 140. Health careprofessional 135 b may utilize user device 115 b through network 105 toinput and receive information from interoperability module 140 and othercomponents of system 100. In some embodiments, interoperability module140 facilitates health care professional module 120 operating with othermodules, such as patient module 110, pharmacy module 130, DME providermodule 170, and/or insurance module 150.

Pharmacy module 130 may be any suitable combination of hardware and/orsoftware implemented in one or more modules to process data for user 135c, such as a pharmacist, a technician, a pharmacy employee, or any otheremployee working with pharmacist 135 c. In some embodiments, pharmacymodule 130 may be associated with a pharmacy organization or brand,and/or a physical pharmacy store location. Pharmacy module 130 may storeand process data related to pharmacist 135 c (name, NPI number,accreditation and/or schooling), a pharmacy company (name, relatedinsurance companies, locations of stores, NPI number), or a physicalstore of the pharmacy company (address, store hours, NPI number).Pharmacy module 130 may further store and process data relating toprescriptions and prescription fulfillment (e.g., for one or morepatients 135 a), as well as insurance and deductible information. Insome embodiments, system 100 does not include pharmacy module 130, andpharmacist 135 c or the pharmacy itself may store all of the records ininteroperability module 140. Pharmacist 135 c may utilize user device115 c through network 105 to input and receive information frominteroperability module 140 and other components of system 100. In someembodiments, interoperability module 140 facilitates pharmacy module 130operating with other modules, such as patient module 110, health careprofessional module 120, and/or insurance module 130. Interoperabilitymodule 140 may access information from other modules that isinaccessible to pharmacy module 130. For example, interoperabilitymodule 140 may access insurance information of patient 135 a frominsurance module 130 and provide the required portion of data from theinsurance records to pharmacy module 130, such that a prescription maybe filled.

Insurance module 150 may be any suitable combination of hardware and/orsoftware implemented in one or more modules to process data for user 135d, such as an insurance agent or other insurance employee. In someembodiments, insurance module 150 may be associated with an insurancecompany and/or a physical location of an insurance center. Insurancemodule 150 may store and process data related to patient 135 (e.g.,name, address, prescription information, insurance information, medicalcoverage, deductible information). In some embodiments, insurance module150 comprises application program interface (API) database 151 thatstores insurance information. API database 151 may refer to any suitabledevice capable of storing and facilitating retrieval of insurance data.API database 151 may store electronic records regarding insuranceinformation, such as information about patient 135 a, type of insurance,payment requirements, prescription coverage, or any other informationrelated to insurance. API database 151 facilitates determining andprocessing insurance claims, and provides information such as coverage,deductible, copayment, and any other information related to insurance.In some embodiments, interoperability module 140 may access API database151 in order to provide up-to-date coverage information to users 135,such as patient 135 a, health care professional 135 b, and/or pharmacist135 c. In some embodiments, system 100 does not include insurance module150, and insurance agent 135 d or the insurance company itself may storeall of the records in interoperability module 140. Insurance agent 135 dmay utilize user device 115 d through network 105 to input and receiveinformation from interoperability module 140 and other components ofsystem 100. In some embodiments, interoperability module 140 facilitatesinsurance module 150 operating with other modules, such as patientmodule 110, health care professional module 120, DME provider module170, and/or pharmacy module 130. Interoperability module 140 may accesselectronic records of insurance information that may be inaccessible toother modules. Interoperability module 140 may extract portions ofelectronic records of insurance information to facilitate the operationof other modules. For example, interoperability module 140 may extract aportion of data related to coverage of a prescription drug and deliverthat portion of data to pharmacy module 130, such that pharmacy module130 may fulfill the prescription and charge patient 135 a accordingly.

In some embodiments, DME provider module 170 may be any suitablecombination of hardware and/or software implemented in one or moremodules to process data regarding medical equipment for patient 135 a byemployee 135 e. DME provider module 170 may store and process datarelated to patient 135 a (e.g., name, insurance information, medicalequipment needed, medical conditions) in order to provide proper medicalequipment. DME provider module 170 may be associated with a DMEprovider, which may refer to an organization and/or physical location orstore that provides, sells, houses, or develops medical equipment.Patient 135 a may visit the DME provider in order to purchase or receivecertain medical equipment. For example, if patient 135 a has diabetes,patient 135 a may visit a pharmacy to receive insulin, blood glucosestrips, and other necessities, but must to go DME provider to receive aninsulin pump. In some embodiments, DME provider module 170 may be usedto create a profile for one or more DME providers. For example, theprofile may indicate the medical equipment provided, manufacturer, name,address, or any other information associated with the DME provider. Insome embodiments, interoperability module 170 may facilitate associatinga DME provider (e.g., DME provider profile) with other users 135. Forexample, if patient 135 a receives an insulin pump from DME provider,patient 135 a may associate its profile with the profile of the DMEprovider. In this manner, patient 135 a may have DME provider'sinformation readily available, for example, if patient 135 a needs theaddress to pick up medical equipment. In some embodiments,interoperability module 170 facilitates DME provider module 170operating with other modules, such as health care professional module120 and insurance module 150.

Medical conditions database 182 may refer to any suitable device capableof storing information associated with medical conditions. In certainembodiments, medical conditions database 182 may store various medicalconditions, along with associated information, such as a formal medicalname, an indication number, a key number, symptoms, diagnosis,treatment, associated prescriptions, or any other associatedinformation. For example, medical conditions database 182 may includeCurrent Procedural Terminology (CPT) codes, which may have a specifickey number tied to a medical condition or procedure. As another example,medical conditions database 182 may include ICD-9-CM Diagnosis andProcedure Codes, which may have a specific key number tied to anymedical condition or diagnosis. Providing a key number increases theexactness of a diagnoses medical condition. For example, if patient 135a simply included “diabetes” in the profile of patient 135, it isunclear whether that is type 1 diabetes, type 2 diabetes, or gestationaldiabetes. By including an exact key number, medical conditions database182 provides further accurate and specific information regarding amedical condition. In some embodiments, interoperability module 140 maysearch medical conditions database 182 to find a medical condition toadd to a user profile. For example, after a diagnosis, patient 135 a orhealth care professional 135 b may be adding a medical condition to theprofile of patient 135 a. Then, when a different user 135 (e.g., healthcare professional 135 b or pharmacist 135 c) views a profile of patient135 a, the most accurate description of the medical condition associatedwith patient 135 a is provided.

NPI number database 183 may refer to any suitable device capable ofstoring information associated with a number of health careprofessionals 135 b, pharmacists 135 c, and pharmacies. In certainembodiments, NPI number database 183 may store information associatedwith the professionals, such as NPI number, name, NPI type, primarypractice address, phone number, taxonomy, enumeration date, status,state, license number, or any other information associated with theprofessionals. In certain embodiments, interoperability module 140 mayaccess and search through NPI database 183 to find health careprofessional 135 b. For example, health care professional 135 b maycreate a profile in interoperability module 140 and want to associate aNPI number with the profile. Interoperability module 140 may receive asearch request from health care professional 135 b (e.g., receive a lastname), and then search NPI number database 183 for a match.Interoperability module 140 may display the matching results such thathealth care professional 135 b may select among the results, and thenassociate the NPI number with the profile of health care professional135 b. By including a NPI number with a profile of user 135,interoperability module 140 provides additional verification that theprofessional is properly accredited based on the patient's needs. Insome embodiments, interoperability module 140 may search NPI numberdatabase 183 for pharmacists 135 c, pharmacy organizations, and/orindividual pharmacy locations within a pharmacy organization.

DEA number database 184 may refer to any suitable device capable ofstoring information associated with a number of health careprofessionals 135 b, pharmacies, or organizations authorized toprescribe certain controlled substances. In some embodiments,interoperability module 140 may access and search DEA number database184 to find health care professional 135 b. For example, health careprofessional 135 b (e.g., a doctor) may create a profile ininteroperability module 140 and want to associate a DEA number with theprofile. Interoperability module 140 may receive a search request fromhealth care professional 135 b (e.g., receive a last name), and thensearch DEA number database 183 for a match. Interoperability module 140may display the matching results such that health care professional 135b may select among the results, and then associate the DEA number withthe profile of health care professional 135 b. By including a DEA numberwith a profile of user 135, interoperability module 140 providesadditional verification that the professional a patient may see isproperly accredited based on the patient's needs.

NCPDP database 185 may refer to any suitable device capable of storinginformation associated with health care professionals 135 b, pharmacists135 c, and pharmacies related to particular drugs and medications. NCPDPdatabase 185 may have additional information related to health careprofessionals 135 b and particular pharmacies. In some embodiments,interoperability module 140 may access data from NCPDP and store inmemory 160 such that users 135 a may associate the information withcertain profiles or organizations.

NDC database 181 may refer to any suitable device capable of storinginformation associated with medications, drugs, and/or drug products.NDC database 181 may store unique and universal product identifiers(e.g., a three-segment number) for human drugs (e.g., prescriptiondrugs, over-the-counter drugs, and insulin products) as well asinformation associated with the drug (e.g., manufacturer, product name,labeler, product, package size, or any information associated with thedrug). In some embodiments, interoperability module 140 may access andsearch through NDC database 181 to identify certain drugs. For example,if patient 135 a has a cold and buys cold medicine, patient 135 a mayscan in a barcode for and/or enter the cold medicine's NDC number.Interoperability module 140 may use the NDC number to search NDCdatabase 181 and identify the specific medicine that patient 135 a haspurchased. Interoperability module 135 may further associate the NDCnumber (and/or corresponding drug information) to a profile of patient135 a. Continuing the example, if patient 135 a seeks assistance fromhealth care professional 135 b, then health care professional 135 b mayview the profile of patient 135 a and determine which drugs that patient135 a has taken in order to better assess the condition of patient 135a.

HCPCS database 186 may refer to any suitable device capable of storinginformation associated with medical supplies, durable medical goods,and/or medical devices. For example, there may be HCPCS numbersassociated with medical devices like oxygen equipment and accessories,nebulizers, hospital beds, patient lifts, crutches, insulin pumps, orany other medical devices or equipment. HCPCS database 186 may storeunique and universal product identifiers for medical devices andequipment that is not associated with any particular brand. For example,if patient 135 a requires an insulin pump, interoperability module maydetermine the HCPCS number associated with the type of insulin pumpneeded. By using the HCPCS number associated with the insulin pump,interoperability module 140 ensures that the correct pump (e.g., withappropriate functionality) is selected. There may be many brandsassociated with a particular HCPCS number for the insulin pump. Forexample, the insurance of patient 135 a may only cover certain brands ofinsulin pump, and interoperability module 140 may access API database151 to determine which brands are covered.

Interoperability module 140 may refer to any suitable combination ofhardware and/or software implemented in one or more modules to processdata and provide the described functions and operations. In someembodiments, the functions and operations described herein may beperformed by a pool of interoperability modules 140. In someembodiments, interoperability module 140 may include, for example, amainframe, server, host computer, workstation, web server, file server,a personal computer such as a laptop, or any other suitable deviceoperable to process data. In some embodiments, interoperability module140 may execute any suitable operating system such as IBM'szSeries/Operating System (z/OS), MS-DOS, PC-DOS, MAC-OS, WINDOWS, UNIX,OpenVMS, or any other appropriate operating systems, including futureoperating systems.

In general, interoperability module 140 facilitates interoperabilityamong modules and databases in system 100. Because information andelectronic records within each module is often inaccessible orincompatible with other modules, interoperability module 140 may analyzethe extracted data and create an electronic record in a different formatthat may be recognized by and compatible with another module.Interoperability module 140 may further transmit the new electronicrecord to the module such that it may accurately use the information toprovide health care services. In some embodiments, interoperabilitymodule 140 may include processor 155, memory 160, and interface 165.

Memory 160 may refer to any suitable device capable of storing andfacilitating retrieval of data and/or instructions. Examples of memory160 include computer memory (for example, RAM or ROM), mass storagemedia (for example, a hard disk), removable storage media (for example,a CD or a DVD), database and/or network storage (for example, a server),and/or or any other volatile or non-volatile, non-transitorycomputer-readable memory devices that store one or more files, lists,tables, or other arrangements of information. Although FIG. 1illustrates memory 160 as internal to interoperability module 140, itshould be understood that memory 160 may be internal or external tointeroperability module 140, depending on particular implementations.Also, memory 160 may be separate from or integral to other memorydevices to achieve any suitable arrangement of memory devices for use insystem 100.

Memory 160 is generally operable to store electronic records, profilesof users 135, profiles of organizations (e.g., pharmacies, DMEproviders, doctor's offices or groups), logic 162, and rules 164. Logic162 generally refers to algorithms, code, tables, and/or other suitableinstructions for performing the described functions and operations.Rules 164 generally refer to policies or directions for analyzingelectronic records and data, extracting data from electronic records,creating electronic records using different data structures, andtransmitting electronic records to various modules in system 100. Rules164 may be predetermined or predefined, but may also be updated oramended based on the needs of patients, health care professionals,pharmacies, and insurance companies.

Memory 160 communicatively couples to processor 155. Processor 155 isgenerally operable to execute logic 162 stored in memory 160 to analyzeelectronic records having a particular data structure, extracting datafrom the electronic records, and creating additional electronic recordsin a format compatible with other modules in system 100, according tothe disclosure. Processor 155 may comprise any suitable combination ofhardware and software implemented in one or more modules to executeinstructions and manipulate data to perform the described functions forinteroperability module 140. In some embodiments, processor 155 mayinclude, for example, one or more computers, one or more centralprocessing units (CPUs), one or more microprocessors, one or moreapplications, and/or other logic.

In some embodiments, communication interface 165 (I/F) iscommunicatively coupled to processor 155 and may refer to any suitabledevice operable to receive input (e.g., electronic records and otherhealth care data) for interoperability module 140, transmit output(e.g., reformatted electronic records and information) frominteroperability module 140, perform suitable processing of the input oroutput or both, communicate to other devices, or any combination of thepreceding. Communication interface 165 may include appropriate hardware(e.g., modem, network interface card, etc.) and software, includingprotocol conversion and data processing capabilities, to communicatethrough network 105 or other communication system that allowsinteroperability module 140 to communicate to other devices.Communication interface 165 may include one or more ports, conversionsoftware, or both. In general, communication interface 165 may retrieveelectronic records, profiles, and other data from memory 160, and mayretrieve information from databases (e.g., medical conditions database182, NPI number database 183, DEA number database 184, NCPDP database185, and NDC database 181) and send information to health care modules(e.g., patient module 110, health care professional module 120, pharmacymodule 130, insurance module 150, and DME provider module).

In operation, logic 162 and rules 164, upon execution by processor 155,facilitate interoperability among modules in system 100. Logic 162 andrules 164 also facilitate receiving electronic records from anorganization, analyzing the electronic record, extracting data from theelectronic record, and creating a second electronic record with a datastructure that is compatible with another organization.

In some embodiments, interoperability module 140 receives a firstelectronic record from a first health care module, the first electronicrecord having a first data structure. The first health care module maybe patient module 100, health care professional module 120, pharmacymodule 130, DME provider module 170, insurance module 150, or any otherhealth care module. Each module may have a particular data structure,form, format, or system for recording electronic information that is notcompatible with other systems. Although electronic record containspatient information, due to the data format, another module may not beable to accurately read, access, or extract information from the firstelectronic record. For example, health care professional module 120 maytransmit an electronic record containing prescription information. Thedata structure may be a written prescription that is scanned into healthcare professional module 120. Another module in system 100 may not beable to recognize the form, hand writing, or information contained inthe prescription. As another example, insurance module 150 may containits insurance information for a patient using particular codes and codenumbers regarding the plan, prescriptions, and coverage. Another modulein system 100 may not recognize the structure or be able to determinecoverage information from the electronic record of insurance module 150.Thus, interoperability module 140 may receive the electronic recordsbefore transmitting to the intended recipient module.

In some embodiments, interoperability module 140 receives a thirdelectronic record from a first health care database, the thirdelectronic record having a third data structure. The health caredatabase may be medical conditions database 182, NPI number database183, DEA number database 184, NCPDP database 185, and NDC database 181,or any other health care database. Interoperability module 140 mayaccess these databases to receive additional information. For example,when setting up a patient profile, interoperability module 140 may addand associate medical conditions to a patient profile. The informationcontained in medical conditions database 182 may be in a particularformat that is not recognizable by or compatible with other health caremodules, and/or contain superfluous information that is not required. Asanother example, when interoperability module 140 creates a health careprofessional profile, it may add information from registered websitessuch as the NPI number database 183 and DEA number database 184. Otherhealth care modules may not understand the significance of the numbersbeing associated with a health care professional profile and thusinteroperability module 140 may first receive the information todetermine its significance.

In some embodiments, interoperability module 140 analyzes the firstelectronic record having the first data structure. Interoperabilitymodule 140 may analyze the record to determine the information that itcontains and the significance of the data. For example, if health careprofessional module 120 transmits a prescription for a drug or medicaldevice, interoperability module 140 may determine the medication, typeof device, dosage, and/or instructions associated with theprescriptions. As another example, if interoperability module 140accesses NPI number database 183, it may determine that a NPI numberdoes not exist for a health care professional.

In some embodiments, interoperability module 140, based on the analysis,extracts a portion of data from the first electronic record.Interoperability module 140 may only extract information relevant toother modules in system 100. For example, when accessing NPI numberdatabase 183, it may extract certain information associated with ahealth care professionals profile (e.g., address, taxonomy, registrationinformation), but not other information (NPI number itself) that is notrelevant to the other system modules.

In some embodiments, interoperability module 140 creates a secondelectronic record using the portion of data from the first electronicrecord, the second electronic record having a second data structure, andthe second data structure is configured to be compatible with a secondhealth care module. Interoperability module 140 may have a uniformsecond data structure that is compatible with each module of system 100.For example, interoperability module 140 may take the extracted data andadd it to a particular user profile, such that the modules may accessand extract data from the profiles. In some embodiments,interoperability module 140 may create a unique second data structurethat is compatible only with a specific second health care module. Forexample, when sending prescription information to pharmacy module 130,interoperability module 140 may populate a specific electronic formrequired by pharmacy module 130 to process and fulfill the prescription.

In some embodiments, interoperability module 140 is further configuredto transmit the second electronic record to the second health caremodule. If the second data format is unique to the second heath caremodule, then the electronic record itself may be sent and then analyzedinternally by the second health care module. If the second data formatis universal for all health care modules, interoperability module 140may display the data and/or transmit. For example, if the secondelectronic record is contained within a user profile, the health caremodule may access the data by viewing the profile itself, rather thanreceiving the electronic record.

In some embodiments, interoperability module 140 facilitates creatingprofiles for users 135 and organizations (e.g., pharmacies, doctor'soffices, DME providers) that may be viewed, accessed, and associatedwith modules in system 100 and/or other profiles. Profiles may store andincorporate information for users 135 or organizations that may beuseful for other users 135. As examples, a profile for patient 135 a mayinclude name, photo, date of birth, medical conditions, allergies,vaccinations, active prescriptions (e.g., from all pharmacies),insurance companies (and associated profile), preferred pharmacies (andassociated profiles), emergency contacts (and associated profiles), orany other information related to patient 135 a. As another example, aprofile for health care professional 135 b may include name, specialty,NPI number, and DEA number. Further, a profile for pharmacist 135 c mayinclude name, pharmacy affiliation (e.g., large pharmacy brand orphysical pharmacy store or location), and NPI number. Finally,interoperability module 140 may facilitate creating profiles fororganizations in system 100. For example, pharmacy brand may have aprofile (e.g., CVS, Walgreens) and each individual location (e.g., CVSpharmacy on 123 Main Street) may have a profile. In this example,interoperability module 140 may associate the profile of patient 135 awith the profile of a specific pharmacy to indicate that is thepreferred pharmacy location to have prescriptions filled. By associatingprofiles, interoperability module 140 may recognize the pharmacy as apreferred pharmacy for patient 135 a, and facilitate health careprofessional module 120 automatically transmitting a prescription to thecorrect pharmacy for patient 135 a.

Profiles may organize all important health information for patient 135 ain an efficient and easily tracked manner. Other modules or users (e.g.,health care professional module 120 and/or health care professional 135b) may access a profile of patient 135 a to retrieve information aboutpatient 135 a. For example, interoperability module 140 may facilitatehealth care professional module 120 retrieving insurance informationfrom the profile of patient 135 a so that health care professionalmodule 120 may incorporate that information into its billing process,thereby conserving computational resources and bandwidth expended ingathering the information during a visit of patient 135 a to the officeand/or contacting an insurance company directly.

By creating profiles for patient 135 a, interoperability module 140 mayfacilitate patient 135 a sharing their health information with othermodules or users 135 such that each has the most up-to-date healthinformation of patient 135 a. In some embodiments, profiles may havevarious levels of restriction and access. For example, a profile ofpatient 135 a may not be accessed by another patient 135 a in system 100without permission being granted first. In some embodiments, only aportion of a profile of patient 135 a may be accessed. For example,interoperability module 140 may provide insurance module 150 access toportions of a profile, such as a name, insurance information, associatedhealth care professionals 135 b, and prescription information of patient135 a, but will not provide access to more private aspects such asmedical conditions and prescriptions unrelated to insurance. The processinteroperability module 140 may use to create, establish, and addinformation to profiles for various users 135 is shown in FIG. 2 anddiscussed in more detail below.

In some embodiments, interoperability module 140 accesses informationfrom database(s) in system 100, extracts relevant information, andcreates an electronic record in an appropriate format for a specificmodule. For example, interoperability module 140 may analyze theinformation provided by NPI number database 183, and extract certaininformation from NPI number database 183 based on the analysis. Forexample, interoperability module 140 may retrieve only address andcontact information for a pharmacy, rather than all informationassociated with the pharmacy. Interoperability module 140 may furthercreate a data format for the extracted information in the form that maybe accessed by various modules in system 100. For example,interoperability module 140 may use the retrieved information to createa profile for the pharmacy or provide a contact information record to besent to another module. Interoperability module 140 may access andextract information from any of the databases in system 100, and createan electronic record in an appropriate format for any module of system100.

In some embodiments, interoperability module 140 facilitates trackingand storing information related to medications, food, or other itemsingested by patient 135 a. Interoperability module 140 may receiveinformation through patient module 110 and/or user device 115 a, forexample, scanning in a bar code on a food item or providing a NDC numberof a medication. This may provide an efficient way for patient 135 a toincorporate additional health information into the profile of patient135 a, and to provide a complete view of the health of patient to otherusers 135 in system 100. For example, by scanning all over-the-counterproducts, interoperability module 140 may determine whether any of theproducts may have an interaction with a prescription being taken.Interoperability module may alert patient 135 a through patient module110 not to use or purchase an over-the-counter product while taking acertain prescription saved in a user profile.

In certain embodiments, interoperability module 140 may facilitatestoring information about and managing all prescriptions of patient 135a in the profile. The profile may include information about eachprescription, such as name, status, associated pharmacy, associatedhealth care professional(s) 135 b, photos, dosage instructions, or anyother information related to the prescription. By storing informationabout all prescriptions in one profile, patient 135 a may readily accessand manage the prescriptions. For example, the user profile of patient135 a in interoperability module 140 may facilitate transferringprescriptions to one or more pharmacies, submitting a request for arefill to health care professional module 120 and/or pharmacy module130, and access any information about prescriptions. As an example,patient 135 a may utilize patient module 110 to review prescriptioninformation and request any changes or refills that may be transmittedto health care professional module 120 by interoperability module 140,rather than patient 135 a having to call or otherwise contact healthcare professional 135 b to make any changes. Interoperability module 140provides an efficient management, storage, and editing techniqueregarding prescriptions.

In certain embodiments, interoperability module 140 may process aprescription for patient 135 a by health care professional 135 b.Interoperability module 140 may receive prescription information fromhealth care professional module 120. In some embodiments,interoperability module 140 may access API database 151 to determinewhether a prescription is covered by insurance of patient 135 a, anddetermine co-pay and deductible information automatically.Interoperability module 140 may provide this information to health careprofessional module 120 and/or patient module 110 so that patient 135 aand/or health care professional 135 b may receive real time feedbackabout whether a prescription is covered or not. In some embodiments,interoperability module 140 may determine alternative prescriptions thatwould provide the same treatment. Interoperability module 140 may accessNDC database 181, medical conditions database 182, or another databaseto determine alternative prescriptions. As an example, if health careprofessional 135 b submits a name-brand prescription, interoperabilitymodule 140 may determine that the name-brand is not covered by theinsurance of patient 135 a and provide alternative prescriptions thatprovide the same treatment and are covered by insurance. The processinteroperability module 140 may use to manage prescriptions for patients135 a is shown in FIG. 3 and FIG. 4 , as discussed in more detail below.

Interoperability module 140 may further transmit a prescription formedication or medical device to pharmacy module 130 and/or DME providermodule 170. Interoperability module 140 may transmit the prescription topharmacy module 130 in response to determining whether insurance coversthe prescription. Interoperability module 140 may receive informationfrom health care professional module 120 as an electronic record andtranslate it into a record format compatible with pharmacy module 130.For example, health care professional 135 b may scan in a writtenprescription, analyze the writing, and extract the data that needs to beprovided to pharmacy module 130. Interoperability module 140 may furtherextract information from the profile of health care professional 135 band combine it with the data extracted from the prescription receivedfrom health care professional module 120. Interoperability module 140may create an additional electronic record in a format compatible withpharmacy module 130 and then transmit the prescription to pharmacymodule 130 such that an associated pharmacy may fulfill the prescriptionfor patient 135. By creating an electronic record in an appropriateformat with the required information, interoperability module 140facilitates communication between health care professional module 120and pharmacy module 130 without concern for compatibility.Interoperability module 140 extracts only necessary data, therebyconserving computational resources, bandwidth, and memory that would beconsumed by each module reentering the data for the prescription andmaintaining a duplicate copy of the electronic record for theprescription.

In certain embodiments, interoperability module 170 determines insurancecoverage for particular prescriptions and facilitates exchange ofinsurance information. For example, interoperability module 170 mayaccess API database 151 from insurance module 150 to get payment anddeductible information for patient 135 a. interoperability module 170may provide the necessary data from API database 151 to pharmacy module130 and/or DME provider module 170 such that a pharmacy and/or DMEprovider may prepare and fulfill the medical equipment and/orprescription for patient 135 a and have deductible information in orderto charge patient 135 a an appropriate amount for the medical equipment.

In particular embodiments, interoperability module 140 may provideupdates on the status of a prescription. Interoperability module 140 mayprovide updates to patient 135 a (e.g., through patient module 110and/or an alert or message to user device 115 a). Status updates mayinclude, for example, “new prescription on file,” when a newprescription is added; “being filled,” when a pharmacy accepted theorder and started preparing it; “ready for pickup,” notifying user 135that an order is complete and patient 135 a may pick it up from thepharmacy; “needs to be discussed,” indicating there are some questionsabout the prescription that prevent pharmacy from fulfilling it;“filled;” indicating patient 135 a has received the prescription and isusing it as prescribed, or any other status update that may be usefulfor user 135 to know. Interoperability module 140 may provide statusupdates to any user 135 in system 100 through the respective module. Forexample, health care professional 135 b may receive updates throughhealth care professional module 120 by accessing a profile of patient135 a. Pharmacist 135 c may receive updates through pharmacy module 130,and/or may be able to generate reports about the outstandingprescriptions at a particular pharmacy location.

In some embodiments, interoperability module 140 may facilitatetransferring a prescription from one pharmacy to another.Interoperability module 140 may initiate a transfer based on a change ininsurance information of patient 135 a. For example, if the insurance ofpatient 135 a changes such that prescriptions may only be filled by acertain pharmacy organization, interoperability module 140 may transferthe prescription such that it is filled by a pharmacy associated withthe insurance. In some embodiments, interoperability module 140 mayreceive a request from user 135 (e.g., patient 135 a, health careprofessional 135 b) via a module (e.g., patient module 110 and/or healthcare professional module 120) to transfer the prescription.Interoperability module 140 may transfer the prescription by sending anelectronic record containing the information about the prescription topharmacy module 130 associated with the new pharmacy. In someembodiments, interoperability module 140 may also notify the oldpharmacy through the associated pharmacy module 130 that theprescription has been transferred.

In particular embodiments, interoperability module 140 facilitatestransmitting messages among modules in system 100. Interoperabilitymodule 140 may provide access to a messaging center for all modules insystem 100. The messaging center may facilitate communication among themodules by allowing each to create a conversation with another. Forexample, interoperability module 140 facilitates pharmacist 135accessing messaging center through pharmacy module 130 and creating anew conversation with health care professional 135 b through health careprofessional module 120. Interoperability module 140 transmits messagesback and forth such that pharmacist 135 c and health care professional135 b may be in real-time communication. Interoperability module 140 mayfurther facilitate a group conversation, for example, to loop in patient135 a and/or insurance agent 135 d. Messages may include a “read” or“unread” identification notifying user 135 about a new query.Interoperability module 140 may include standard responses to facilitatefaster and more efficient communication. Interoperability module 140 mayprovide a health care professional 135 b a standard response of“approved” or “switch to generic” that would be repeatedly used, therebyconserving time between answers. In some embodiments, messages may besaved until accessed or changed by the appropriate user 135.

In some embodiments, interoperability module 140 may generate a reportregarding prescriptions of patient 135 a. Interoperability module 140may access the profile of patient 135 a and review any information aboutprescriptions of patient 135 a. Information about prescriptions caninclude filled prescriptions, cost of the filled prescriptions,prescriptions in other statuses (e.g., being filled, ready for pick-up),and estimated costs for open but not filled prescriptions.Interoperability module 140 may further access information aboutfulfillment centers and their contacts (e.g., pharmacist 135). In someembodiments, interoperability module 140 may generate the report inresponse to receiving a request. The request may be received from amodule in system 100 (e.g., insurance module 150), and may includeinformation such as a time period for the report (e.g., the past 24hours, the past week, the past 30 days, the past 90 days, the past year,or any time period). In some embodiments, interoperability module 140may transmit the report to insurance module 150, patient module 110,health care professional module 120, and/or pharmacy module 130.

A component of system 100 may include an interface, logic, memory,and/or other suitable element. An interface receives input, sendsoutput, processes the input and/or output and/or performs other suitableoperations. An interface may comprise hardware and/or software. Logicperforms the operation of the component, for example, logic executesinstructions to generate output from input. Logic may include hardware,software, and/or other logic. Logic may be encoded in one or moretangible media, such as a computer-readable medium or any other suitabletangible medium, and may perform operations when executed by a computer.Certain logic, such as a processor, may manage the operation of acomponent. Examples of a processor include one or more computers, one ormore microprocessors, one or more applications, and/or other logic.

Modifications, additions, or omissions may be made to the systemsdescribed herein without departing from the scope of the disclosure. Forexample, system 100 may include any number of patient modules 110,health care professional modules 120, pharmacy modules 130, DME providermodules 170, insurance modules 150, medical conditions database 182, NPInumber database 183, DEA number database 184, NCPDP database 185, andNDC database 181. As another example, particular functions, such asanalyzing data from databases and creating new electronic records in aformat compatible with modules may be performed by a separate componentand interoperability module 140 receives the information regarding theanalysis and/or electronic records. The components may be integrated orseparated. Moreover, the operations may be performed by more, fewer, orother components. Additionally, the operations may be performed usingany suitable logic comprising software, hardware, and/or other logic. Asused in this document, “each” refers to each member of a set or eachmember of a subset of a set.

FIG. 2 illustrates an example flowchart for a method 200 for varioususers 135 of system 100 to register and create user profiles tofacilitate interoperability among health care modules. In general,method 200 facilitates various users 135 of interoperability module 140of FIG. 1 registering and creating user profiles. Method 200 may beperformed by interoperability module 140, or any other component ofsystem 100. Method 200 may apply to the creation of a profile of anyuser 135 or organization of FIG. 1 , such as patients 135 a, health careprofessionals 135 b, pharmacists or fulfillment employees 135 c,insurance or payee employees 135 d, or DME provider employees 135 e,pharmacies associated with pharmacy module 130, offices associated withhealth care professional module 120, insurance companies associated withinsurance module 150, or any other user or organization of system 100.The steps of method 200 may be repeated as necessary to receive all theinformation to provide and facilitate interoperability between varioushealth care modules. By registering various users 135, interoperabilitymodule 140 may store data in an efficient manner, thus conservingcomputational resources and allowing for faster processing speed.

Method 200 begins at step 201, in some embodiments, whereinteroperability module 140 receives user profile information. Userprofile information may be any information related to the user. Forexample, user profile information may be name, address, date of birth,employment information or any other information related to the user. Insome embodiments, a user may be a caregiver that cares for multiplepatients. Continuing the example, the caregiver may include informationabout the caregiver himself as well as information about the one or morepatients the caregiver may take care of. As another example, the usermay be health care professional 135 b, such as a doctor, nursepractitioner, physician's assistant, nurse or administrative assistantat a health care professional's office. In some embodiments, patient 135a may submit general health information beyond prescription information,such as medical history, and exercise and diet. In some embodiments,interoperability module 140 may receive information about specific foodsand medications taken by patient 135 a. Patient 135 a may input theinformation by scanning barcodes of certain food items, so that thegeneral food intake may be tracked and viewed by other users 135 (e.g.,health care professional 135 b) of system 100. By collecting the userprofile information, interoperability module 140 may register each usersuch that the various health care modules may efficiently communicateand share data.

In general, at steps 203, 215 and 229, in some embodiments,interoperability module 140 determines whether it receives requests tosearch for specific issues that may be included in a user profile. Ateach step, this determination may prompt interoperability module 140 tosearch external databases or internal databases to determine andpotentially add certain information to a user profile. Addinginformation to profiles from external databases provides an efficientway to maintain and share data in the common format among the differenthealth care modules.

At step 203, in some embodiments, interoperability module 140 determineswhether there is a request to search for medical conditions. The requestmay be received through network 105 from user device 115 that submitsthe request. The request may appear as a pop up on the screen thatsolicits whether the user wants to search for medical conditions to addto the user's profile. In some embodiments, medical conditions may be acondition that a patient has, a condition that a patient has had in thepast, a condition that a health care professional is an expert in, acondition that an insurance company provides financial coverage for, acondition that a durable medical provider can provide equipment for, orany other information related to the medical condition. If at step 203,interoperability module 140 determines there has not been a request tosearch for medical conditions, interoperability module 140 continuesfrom step 215, discussed below. If at step 203, interoperability module140 determines there has been a request to search for medicalconditions, interoperability module 140 may access medical conditionsdatabase 182 in step 205. This database may be stored internally orexternally from interoperability module 140. In accessing medicalconditions database 182, interoperability module 140 may use theinformation included in the request to determine any inputs to searchthe medical database. Interoperability module 140 may perform acomparative analysis to determine which medical conditions are relevantor match the medical condition input by the request in step 203.

At step 207, in some embodiments, interoperability module 140 retrievesthe results of the various medical conditions and displays the medicalconditions at step 209. These medical conditions may be displayed onuser device 115 such as a drop down menu that user may view and selectamong. At step 211, in some embodiments, interoperability module 140receives the selection among the displayed medical conditions. Forexample, user 135 may select one or more medical conditions to associatewith the user profile. At step 213, in some embodiments,interoperability module 140 stores the medical condition to associatewith the user profile. In some embodiments, a caregiver may be creatinga user profile for the patient the caregiver takes care of Thus,caregiver 135 a may be able to associate the medical condition with oneor more patient user profiles. In some embodiments, health careprofessional 135 b may be adding information to an existing userprofile. For example, if patient 135 a has visited with health careprofessional 135 b and determined that patient 135 a has a medicalcondition, then health care professional 135 b may add it to the userprofile of patient 135 a. By adding medical conditions to a userprofile, patient 135 a may have access to information about that medicalcondition, such as symptoms, warnings, when to call a health careprofessional for help, certain drugs that may be taken to alleviatecertain symptoms, as well as any other information that may be helpfulto a user. In some embodiments, other health care professionals 135 bmay be able to access a user profile and determine that a user profileis associated with a specific medical condition. This may impact themedications prescribed to the user as well as various treatmenttechniques provided by other health care professionals.

At step 215, in some embodiments, interoperability module 140 determineswhether there is a request to search for health care professionals.Interoperability module 140 may determine that a user profile is beingcreated, and thus may communicate a prompt to user device requestingwhether to add a health care professional to the user profile. Therequest may also include information for the health care professional,such as NPI number, DEA number, name, address, or any other identifyinginformation. This information may be helpful in searching for the healthcare professional in a database. If at step 215, interoperability module140 determines that a request to search for a health care professionalis not received, the method continues to step 229, discussed below. Ifat step 215, interoperability module 140 receives a request to searchfor a health care professional, the method continues to step 217 whereinteroperability module 140 receives health care professional'sinformation. The health care professional's information may be includedwith the request.

Once interoperability module 140 receives the health care professional'sinformation at step 217, interoperability module 140 accesses a healthcare professional database at step 219. The health care professionaldatabase may be an NPI database 183, DEA number database 184, a stateregistry for health care professionals, or any other database that mayhave information about health care professionals. In accessing thehealth care professional database, interoperability module 140 maycompare the health care professional information received at step 217 tothe information in the one or more databases. At step 221,interoperability module 140 may retrieve results of the health careprofessional from the one or more databases and display the varioushealth care professionals at step 223. At step 225, in some embodiments,interoperability module 140 may receive a selection among the displayedhealth care professional from step 223. The user may filter through thedifferent health care professional information displayed at step 223 andselect one or more to associate with the user's profile.

At step 227, interoperability module 140 stores the health careprofessional as associated with the user profile. By associating one ormore health care professionals with the user profile, user 135 may haveinformation about their health care professional 135 b readilyavailable. For example, user may need to call or send a message tohealth care professional 135 b for a question and have the phone numberavailable for access. As another example, another health careprofessional 135 b may want to see information from another health careprofessionals 135 b that patient 135 a visits and can access thatinformation through the user's profile. As another example, a pharmacyor fulfillment organization may want to see the doctor that prescribedpatient 135 a a specific prescription and may readily determine thatinformation by accessing a profile of patient 135 a and seeing whichhealth care professionals 135 b are associated with that user profile.

In some embodiments, steps 215 through 227 may be used by health careprofessionals to create a health care professional profile. Health careprofessional 135 b may then have her own profile such that other userscan associate their profile(s) with the health care professional profilemore readily. In some embodiments, when creating a health careprofessional profile, interoperability module 140 may access multipledatabases to ensure that the health care professional is a registeredprofessional with proper accreditation. For example, interoperabilitymodule 140 may determine whether health care professional 135 b has theability to prescribe certain prescriptions and medications required bypatient 135 a based on the patient's medical conditions. For example, inorder to prescribe certain medications, a health care professional mustbe registered with the Drug Enforcement Administration and have a DEAnumber that can be verified by searching DEA number database 184.

At step 220, in some embodiments, interoperability module 140 determineswhether there is a request to search for pharmacies. In someembodiments, step 229 implements some of the techniques performed atsteps 215 and 203. If at step 229, interoperability module 140 has notreceived a request to search for pharmacies, interoperability module 140continues to step 243, described below. If at step 229 interoperabilitymodule 140 receives a request to search for pharmacies, the methodcontinues from step 231.

At step 231, in some embodiments, interoperability module 140 accessesinsurance company information from API database 151. API database 151may include information about coverage for patient 135 a as well asapproved pharmacies. In order for user 135 to associate with one or morepharmacies, interoperability module 140 may access the insuranceinformation of user 135 a to determine which pharmacies may be bestsuited for patient 135 a and/or health care professional 135 b toutilize in fulfilling prescriptions. At step 233, interoperabilitymodule 140 may retrieve the results of the approved pharmacies.Accordingly, user 135 may only fill prescriptions at approved pharmaciesand thus reduce the risk of filling prescriptions at a pharmacy that isnot covered and having to pay additional expenses.

In some embodiments, interoperability module 140 may use the location ofuser 135 to determine the most suitable pharmacy. At step 235, in someembodiments, interoperability module 140 compares the location ofapproved pharmacies retrieved in step 233 to the location of the user.The location of user 135 may be the current location of user 135 asdetermined using location information of user device 115, an addressassociated with the user profile (e.g., a patient's home or place ofwork), or any other location preference. In this comparison,interoperability module 140 may determine the approved pharmacies thatare in the appropriate radius of the location of user 135. At step 237,interoperability module 140 may display the results of the pharmaciesbased on the comparison. When the results are displayed, user 135 may,for example, select one or more pharmacies using a drop-down menu andclick on the pharmacies to add. At step 239, in some embodiments,interoperability module 140 receives the selection among the displayedpharmacies, and at step 241, stores the pharmacy or pharmacies asassociated with the profile of user 135. By associating pharmacies witha user profile, other health care professionals 135 b may access thatinformation to fill prescriptions efficiently. For example, health careprofessional 135 b who is refilling a prescription may submit the refillrequest through health care professional module 120 such thatinteroperability module 140 determines the closest pharmacy to user 135b and automatically transmits the prescription to the associatedpharmacy module 130. For example, if the user is out of state and needsthe prescription, the prescription may be automatically sent to thenearest pharmacy for user 135. As another example, user 135 maypreference certain pharmacies for certain health care professionals 135b. In some embodiments, user 135 may associate one or more pharmacieswith the user profile. As another example, if the user profile is beingcreated for an insurance company, the insurance company may associatevarious pharmacies with the insurance company's user profile. In thatway, patient 135 a, health care professional 135 b, or pharmacist 135 cmay see whether the insurance company is associated with a specificpharmacy and whether prescriptions may be filled there. For example, oneinsurance company may only fill prescriptions at a CVS while another mayonly use Walgreens. When submitting a prescription to a pharmacy, healthcare professional 135 b may want to understand what pharmacies arecovered by a patient's insurance before submitting the prescription.

Finally, at step 243, in some embodiments, interoperability module 140determines whether registration is complete. Interoperability module 140may display a prompt on the screen of user device 115 asking whetheruser 135 has completed registration. User 135 may select thatregistration is complete and interoperability module 140 may receiveconfirmation that registration is complete in step 245. In receivingconfirmation, interoperability module 140 may save all newly receiveddata and properly associate received information with the user profilesuch that others in the system may be able to access the associatedinformation.

Modifications, additions, or omissions may be made to the methodsdescribed herein without departing from the scope of the disclosure. Forexample, the steps may be combined, modified, or deleted whereappropriate, and additional steps may be added. For example, steps 243and 245 may be omitted; rather than query whether registration iscomplete, interoperability module 140 may automatically save the resultsand profile elements received. Additionally, the steps may be performedin any suitable order without departing from the scope of the presentdisclosure. For example, searching for associated pharmacies at steps229-241 may begin the registration process and thus occur before step203. While discussed as interoperability module 140 performing thesteps, any suitable component of system 100 may perform one or moresteps of the method.

FIG. 3 illustrates an example flowchart for method 300 for facilitatinginteroperability between health care professional module 120 andinsurance module 150. In general, method 300 illustrates determiningwhether a drug prescription is covered by a patient's insurance. Byproviding that information to health care professional 135 b throughhealth care professional module 120, health care professional 135 b maymake changes to the prescription before submitting it for fulfillment.For example, if health care professional 135 b prescribes the name brandof the prescription, interoperability module 140 may determine that theprescription is not covered by the patient's insurance and provide analert. Continuing the example, after receiving the alert, health careprofessional 135 b may alter the prescription to a generic drug that iscovered by a patient's insurance. Thus, method 300 provides for a moreefficient way to determine prescription coverage and reduce thelikelihood that a prescription is not covered by a patient's insurance;thereby conserving resources and not sending multiple requests forinsurance information and fulfilling incorrect prescriptions.

Method 300 begins at step 301, in some embodiments, whereinteroperability module 140 receives the prescription from health careprofessional module 120. Interoperability module 140 may receive theprescription by accessing it in a patient's electronic health records,receiving entry of new prescription information, or receiving an RXbarcode from a prescription label or box. When interoperability module140 receives the prescription, it may receive information about the drugincluding the ingredients, side effects, conditions it is meant totreat, and any other information that may be useful for health careprofessional 135 b or patient 135 a. The prescription may also includedirections for taking the prescription such as number of doses, timesper day, items to consume with the prescription, as well as items toavoid. Interoperability module 140 may receive the prescription in aparticular data format that requires analysis to extract the relevantinformation. Interoperability module 140 may analyze the contents of thereceived prescription and extract portions of the data such that theprescription may be processed.

At step 303, in some embodiments, interoperability module 140 determineswhether the prescription is verified or covered by a patient'sinsurance. If, at step 303 interoperability module 140 determines theprescription is covered, method 300 continues to step 313, discussedbelow. If interoperability module 140 determines the prescription is notcovered at step 303, the method continues from step 305, in someembodiments. In order to verify the prescription, interoperabilitymodule 140 may, at step 305 receive information from the insurancecompany, such as information from API database 151 that provides detailsabout the insurance coverage of patient 135 a and prescription drugdetails. Interoperability module 140 may access API information from apatient's insurance to determine whether the prescription is covered bythe patient's insurance. Interoperability module 140 may store thisinformation in a memory (e.g., memory 160 of FIG. 1 ); therebyconserving computational resources and not accessing API database 151each time the prescription is refilled. Instead, interoperability module140 may store an indication that a prescription is covered, and thenperiodically check API database 151 to determine whether any changes ininsurance have occurred.

At step 307, in some embodiments, interoperability module 140 determinesoptions of covered prescriptions related to the prescription received instep 301. Interoperability module 140 may analyze the API information todetermine what drugs would be covered by the insurance company andfurther determine what drugs are appropriate replacements for theprescription that was submitted. Interoperability module 140 may accessinformation from a database that indicates corresponding or replacementmedications for certain other types of medications. Interoperabilitymodule 140 may then compare the medications to determine an appropriatereplacement. At step 309, in some embodiments, interoperability module140 displays the options determined in step 307. These options andinformation regarding the drugs may be displayed to health careprofessional 135 b through health care professional module 120, suchthat a replacement prescription may be selected from among the variousoptions for an adequate replacement prescription. At step 311, in someembodiments, interoperability module 140 receives selection of the newprescription from the options displayed in step 309 on a screen, anddetermines that selection is the prescription to be filled.Interoperability module 140 may further receive information about theprescription such as coverage information, deductible information, sideeffects information, and/or any other information related to the drugsand prescription.

Interoperability module 140 then determines whether more information isneeded before filling a prescription at step 313. Interoperabilitymodule 140 may determine it requires additional patient information,prescription information, drug dosage and usage requirements,instructions, medical conditions suffered by the patient, or any otherinformation that may be required such that the prescription may befulfilled by a pharmacy and used by patient 135 a. If at step 313,interoperability module 140 determines that more information is notneeded, method continues to step 321, discussed below. If at step 313,interoperability module 140 determines that more information is needed,method 300 continues from step 315 where interoperability module 140determines what information is needed. Interoperability module 140 mayhave access to certain information or permissions a pharmacy must havebefore filling a prescription. By performing a check on this informationand/or permissions before sending the prescription for fulfillment,interoperability module 140 conserves bandwidth that would be expendedby having to pause a fulfillment once it is has been transmitted topharmacy module 130. At step 317, in some embodiments, interoperabilitymodule 140 sends a message to health care professional 135 b via healthcare professional module 120 on the information that is needed and thenreceives the updated information in step 319. Health care professional135 b may enter this information through user device 115 b. In someembodiments, method 300 may analyze and extract the information andcreate a new electronic record in a format that will be compatible withpharmacy module 130.

Method 300 continues to step 321 where interoperability module 140transmits the prescription. The prescription may be transmitted topatient module 110 so that patient 135 a may determine what health careprofessional 135 b prescribed to them, as well as information about theprescription. The prescription may also be transmitted to pharmacymodule 130 or other fulfillment organization such that the prescriptionmay be filled for patient 135 a to come pick up.

At step 323, in some embodiments, interoperability module 140 receivesdeductible information from the insurance company. Interoperabilitymodule 140 may send a request for the information such it receives thedeductible information for this prescription. Interoperability module140 may also determine the deductible information based on the APIdatabase 151 information accessed and/or stored in its system. At step325, in some embodiments, interoperability module 140 displaysprescription coverage and deductible information. This may be displayedto patient 135 a, the insurance company agent 135 d, as well as thepharmacist 135 via patient module 110, insurance module 150, andpharmacy module 130, respectively. After this, the method ends.

Modifications, additions, or omissions may be made to the methodsdescribed herein without departing from the scope of the disclosure. Forexample, the steps may be combined, modified, or deleted whereappropriate, and additional steps may be added. Steps 303 and 305 may becombined such that the prescription is verified based on the informationreceived from insurance module 150. Additionally, the steps may beperformed in any suitable order without departing from the scope of thepresent disclosure. For example, receiving deductible information frominsurance module 150 at step 323 may occur before the prescription istransmitted in step 321. While discussed as interoperability module 140performing the steps, any suitable component of system 100 may performone or more steps of the method.

FIG. 4 illustrates an example flowchart for method 400 facilitatinginteroperability between pharmacy module 130 and health careprofessional module 120. In general, method 400 allows forinteroperability between different systems in the healthcare industry,specifically it involves prescription management and facilitating aprescription being accurately and timely fulfilled by a pharmacy orfulfillment company. By facilitating interaction between a health careprofessional system and a fulfillment company, method 400 conservescomputational resources as well as bandwidth expended by transmittingincompatible electronic records or files.

Method 400 begins at step 401, in some embodiments, whereinteroperability module 140 receives the prescription information. Theprescription information may include coverage information such as apatient's insurance coverage as well as deductible information. Thedeductible information may indicate how much a fulfillment companyshould charge patient 135 a when retrieving the filled prescription. Insome embodiments, interoperability module 140 may further transmit theprescription information to pharmacy module 130 and/or DME providermodule 170 for filling.

At step 403, in some embodiments, interoperability module 140 determineswhether it has received a question from fulfillment module 130 and/orDME provider 170. Interoperability module 140 may continually assesseswhether fulfillment module 130 sends and/or may check for questions atcertain intervals. In some embodiments, interoperability module 140 mayanalyze the received question to determine where to transmit theinquiry. For example, interoperability module 140 may determine healthcare professional 135 b is associated with the prescription.Interoperability module 140 may further determine the information neededby fulfillment module 130 based on the question submitted. Ifinteroperability module 140 determines that a question has not beenreceived after a certain period of time, method 400 continues to step409, as discussed below. If at step 403, interoperability module 140determines that a question has been received from fulfillment module130, method 400 continues to step 405. At step 405, in some embodiments,interoperability module 140 transmits the question to health careprofessional module 120. In some embodiments, the system of electronicrecords for fulfillment module 130 and health care professional module120 may be incompatible such that the information may not be accuratelyreceived. Interoperability module 140 may extract information from thequestion from fulfillment module 130 and create a new electronic recordin a format compatible with health care professional module 120. At thispoint, health care professional module 120 may receive the question anddetermine any answer. Health care professional 135 b may enter theanswer through user device 115 in a particular format or data structure.At step 407, in some embodiments, interoperability module 140 receivesthe answer from health care professional 135 b, for example, andtransmits the answer to fulfillment module 130. In certain embodiments,step 403 and 407 may be repeated until fulfillment module 130 receivesanswers to all of the questions to fill a prescription.

At step 409, in some embodiments, interoperability module 140 receivesan indication that the prescription has been filled. Interoperabilitymodule 140 may receive this indication from fulfillment module 130. Insome embodiments, interoperability module 140 may automatically receivean indication from the fulfillment module 130, which may be programmedto send an automatic alert to interoperability module 140.

Method 400 continues at step 411, in some embodiments, whereinteroperability module 140 notifies user 135 that the prescription hasbeen filled. At step 413, in some embodiments, interoperability module140 receives pickup details from fulfillment module 130 regarding whenand how user 135 should pick up the prescription. For example, thenotification may indicate that user 135 must bring a form ofidentification in order to pick up the prescription. As another example,the notification may indicate the time that the prescription will beavailable as well as the pharmacy that has fulfilled the prescription,including pharmacy hours and details. Once interoperability module 140receives the pickup details at step 413, interoperability module 140 maytransmit the updated notification to user 135 at step 415, in someembodiments, with these pickup details. The method ends after step 415.

Modifications, additions, or omissions may be made to the methodsdescribed herein without departing from the scope of the disclosure. Forexample, the steps may be combined, modified, or deleted whereappropriate, and additional steps may be added. Step 411 may be omittedand steps 409 and 413 may be combined such that a user may be notifiedat step 415 regarding both an indication that the prescription has beenfilled and the pickup details. As another example, a step 402 may beadded for interoperability module 140 to transmit the prescriptionreceived at step 401 to pharmacy module 130. Additionally, the steps maybe performed in any suitable order without departing from the scope ofthe present disclosure. While discussed as interoperability module 140performing the steps, any suitable component of system 100 may performone or more steps of the method.

FIGS. 5A-C illustrates example user profiles that may facilitateinteroperability among health care modules. The user profiles may becreated using the process outlined in method 200 of FIG. 2 and createdand/or utilized by interoperability module 140 of FIG. 1 . FIG. 5Aillustrates an example home page of a user profile (e.g., a patient).The home page may indicate general information associated with a user(e.g., name, date of birth, and medical conditions), list insurancecompanies associated with the user, and include options for moreinformation about the patient (“show all information,” “view allprescriptions,” etc.). In some embodiments, the user profile may grouptogether related pieces of information. For example, the user profilemay show a medical condition of the patient, as well as relatedprescription information such as the drugs and/or medical devices thepatient uses to treat that medical condition. The user profile may alsoshow codes related to the medical condition and prescriptions, such asCPT codes for the medical condition, NDC and HCPCS codes for anyprescriptions of medicine or medical devices. By grouping togetherinformation, the user profile efficiently stores the medical informationfor the user and can quickly identify the medications and/or medicaldevices used by the patient, and for which medical diagnosis each isrelated to. The user profile may contain any information thatfacilitates interoperability among health care modules, and thus FIG. 5Ashould not be construed as a limiting example of what may be included.

FIG. 5B illustrates a prescription tab available on the user profile.The prescription tab may show any number of prescriptions, as well assorting the prescriptions by age, frequency, importance, or any otherfactor. In some embodiments, prescriptions may also be searched. In someembodiments, a prescription may be selected such that more informationabout the prescription is displayed. The prescription tab may containany information related to relevant prescriptions and thus FIG. 5Bshould not be construed as a limiting example of what may be included.

FIG. 5C illustrates a prescription page that includes more detailedinformation about a particular prescription. For example, theprescription page may show the associated health care professional thatprescribed the prescription, any alternatives, date created, dosage anddirections, quantity, and any other information related to theprescription. The prescription page may further include insuranceinformation, such as the company, whether the prescription is covered,copay and deductible information, and any other related information. Theprescription page may further provide an option to start a chat ormessage with a fulfillment center or health care professional so thatthe patient may ask any questions. The prescription page may contain anyinformation related to relevant prescriptions and thus FIG. 5C shouldnot be construed as a limiting example of what may be included.

FIG. 6 illustrates an example interface for creating a new prescriptionand facilitating interoperability between health care professionalmodules, patient modules, and pharmacy and/or DME provider modules. Thenew prescriptions may be created using the process outlined in method300 of FIG. 3 and created and/or utilized by interoperability module 140of FIG. 1 . FIG. 6 illustrates an interface that a health careprofessional may view when entering a new prescription for a patient(e.g., “Example Example”). When interoperability module 140 receives theprescription name and amount, it may automatically determine whether theprescription is covered by the patient's insurance. FIG. 6 illustratesan example where the insurance does not cover the prescription,displaying the insurance information and an indicator that theprescription is not covered (e.g., highlighted text and/or a “no”symbol). Interoperability module 140 may further identify an alternativeprescription (e.g., “Atovastatin”) and display an option for the healthcare professional to “use this product.” Because interoperability module140 is able to automatically determine coverage, a health careprofessional may be notified before providing the prescription topatient and/or transmitting the prescription to a fulfillment company.The interface of health care professional module 120 may contain anyinformation related to users and/or relevant prescriptions and thus FIG.6 should not be construed as a limiting example of what may be included.Technical advantages of particular embodiments of the present disclosureinclude reconfiguring an existing data structure to create a new datastructure to allow health care modules to communicate health careinformation between disparate components. This improvement alleviatescompatibility concerns between different systems components, therebycreating increased flexibility in exchanging electronic records.Additionally, a system may be configured to analyze data in anelectronic record and extract a portion of data from the electronicrecord, thereby conserving the computational resources and bandwidthconsumed by unnecessarily extracting all the data, some of which may beirrelevant.

In an embodiment, a system is configured to create a first user profileand associate the first user profile with other user profiles, therebyconserving the computational resources and bandwidth consumed by addingadditional information contained in other user profiles to the firstuser profile.

In an embodiment, a system is configured to create a second electronicrecord that is compatible with more than one health care module, therebyconserving the computational resources and bandwidth consumed bycreating and maintaining duplicate electronic records, each in adifferent format unique to each health care module.

Other technical advantages of the present disclosure will be readilyapparent to one skilled in the art from the following figures,descriptions, and claims. Moreover, while specific advantages have beenenumerated above, various embodiments may include all, some, or none ofthe enumerated advantages.

Although the present disclosure has been described with severalembodiments, a myriad of changes, variations, alterations,transformations, and modifications may be suggested to one skilled inthe art, and it is intended that the present disclosure encompass suchchanges, variations, alterations, transformations, and modifications asfall within the scope of the appended claims.

What is claimed is:
 1. A system, comprising: a memory configured tostore code configured for extracting data from electronic records andcreating additional electronic records in a desired data structure thatis different from an initial data structure; an interfacecommunicatively coupled with the memory, and configured to: receive afirst electronic record of a patient, the first electronic record havinga first data structure; receive a second electronic record from a firstcomputing device associated with an insurance organization, the secondelectronic record comprising information regarding medical coverage, thesecond electronic record having a second data structure, wherein thesecond data structure is incompatible with a second computing deviceassociated with a patient; a processor communicatively coupled to thememory and the interface, the processor configured to: extract, by atleast executing the code, data relating to a medical service from thefirst electronic record; extract, by at least executing the code, datarelating to medical coverage for the patient from the second electronicrecord; based at least on the extracted data from the first and thesecond electronic records, create, by at least executing the code, athird electronic record comprising data relating to the medical serviceand data relating to the medical coverage, the third electronic recordhaving a third data structure that is compatible with the secondcomputing device, wherein the third data structure is different fromeach of the first and second data structures; and based on the thirdelectronic record, determine whether the medical service is covered forthe patient.
 2. The system of claim 1, the processor further configuredto determine a current procedural terminology (CPT) code related to themedical service.
 3. The system of claim 1, the processor furtherconfigured to: based on the third electronic record, determine that themedical service is covered for the patient; and determine a cost for thepatient.
 4. The system of claim 1, the processor further configured to:based on the third electronic record, determine that the medical serviceis not covered for the patient; and determine a cost for the patient. 5.The system of claim 1, wherein the medical service is related to adental or vision service.
 6. The system of claim 1, the processorfurther configured to: create a profile of the patient based in part onthe first electronic record of the patient; and cause to display theprofile to a health care professional related to the medical service. 7.The system of claim 1, the processor further configured to: receive anindication relating to a medical condition of the patient; and add themedical condition to a profile of the patient.
 8. A non-transitorycomputer-readable medium encoded with logic, the logic, when executed bya processor, operable to: store code configured for extracting data fromelectronic records and creating additional electronic records in adesired data structure that is different from an initial data structure;receive a first electronic record of a patient, the first electronicrecord having a first data structure; receive a second electronic recordfrom a first computing device associated with an insurance organization,the second electronic record comprising information regarding medicalcoverage, the second electronic record having a second data structure,wherein the second data structure is incompatible with a secondcomputing device associated with a patient; extract, by at leastexecuting the code, data relating to a medical service from the firstelectronic record; extract, by at least executing the code, datarelating to medical coverage for the patient from the second electronicrecord; based at least on the extracted data from the first and thesecond electronic records, create, by at least executing the code, athird electronic record comprising data relating to the medical serviceand data relating to the medical coverage, the third electronic recordhaving a third data structure that is compatible with the secondcomputing device, wherein the third data structure is different fromeach of the first and second data structures; and based on the thirdelectronic record, determine whether the medical service is covered forthe patient.
 9. The computer-readable medium of claim 8, wherein thelogic is further operable to determine a current procedural terminology(CPT) code related to the medical service.
 10. The computer-readablemedium of claim 8, wherein the logic is further operable to: based onthe third electronic record, determine that the medical service iscovered for the patient; and determine a cost for the patient.
 11. Thecomputer-readable medium of claim 8, wherein the logic is furtheroperable to: based on the third electronic record, determine that themedical service is not covered for the patient; and determine a cost forthe patient.
 12. The computer-readable medium of claim 8, wherein themedical service is related to a dental or vision service.
 13. Thecomputer-readable medium of claim 8, wherein the logic is furtheroperable to: create a profile of the patient based in part on the firstelectronic record of the patient; and display the profile to a healthcare professional related to the medical service.
 14. Thecomputer-readable medium of claim 8, wherein the logic is furtheroperable to: receive an indication relating to a medical condition ofthe patient; and add the medical condition to a profile of the patient.15. A method comprising: storing code configured for extracting datafrom electronic records and creating additional electronic records in adesired data structure that is different from an initial data structure;receiving, by an interface, a first electronic record of a patient, thefirst electronic record having a first data structure; receiving, by theinterface, a second electronic record from a first computing deviceassociated with an insurance organization, the second electronic recordcomprising information regarding medical coverage, the second electronicrecord having a second data structure, wherein the second data structureis incompatible with a second computing device associated with apatient; extracting, by a processor executing the code, data relating toa medical service from the first electronic record; extracting, by theprocessor executing the code, data relating to medical coverage for thepatient from the second electronic record; based at least on theextracted data from the first and the second electronic records,creating, by the processor executing the code, a third electronic recordcomprising data relating to the medical service and data relating to themedical coverage, the third electronic record having a third datastructure that is compatible with the second computing device, whereinthe third data structure is different from each of the first and seconddata structures; and based on the third electronic record, determining,by the processor, whether the medical service is covered for thepatient.
 16. The method of claim 15, further comprising determining, bythe processor, a current procedural terminology (CPT) code related tothe medical service.
 17. The method of claim 15, further comprising:based on the third electronic record, determining, by the processor,that the medical service is covered for the patient; and determining, bythe processor, a cost for the patient.
 18. The method of claim 15,further comprising: based on the third electronic record, determining,by the processor, that the medical service is not covered for thepatient; and determining, by the processor, a cost for the patient. 19.The method of claim 15, further comprising: creating, by the processor,a profile of the patient based in part on the first electronic record ofthe patient; and displaying, by the interface, the profile to a healthcare professional related to the medical service.
 20. The method ofclaim 15, further comprising: receiving, by the interface, an indicationrelating to a medical condition of the patient; and adding, by theprocessor, the medical condition to a profile of the patient.